Overview
What is MarkLogic Server?
MarkLogic Server is a multi-model database that has both NoSQL and trusted enterprise data management capabilities. The vendor states it is the most secure multi-model database, and it’s deployable in any environment. They state it is an ideal database to…
Mark’it with Logic_9553
Close to perfect NoSQL DB
If you like XML, and you need an enterprise-grade database platform, MarkLogic towers above all others.
Fantastic if it fits into the use-case
MarkLogic- The Swiss Army Knife of data platforms
Can You Bet on It?
MarkLogic - NoSQL with an edge
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Pricing
Low Priority Fixed
$0.01
Standard Reserved
$0.07
Standard On-Demand
$0.13
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Details
- About
- Competitors
- Tech Details
- FAQs
What is MarkLogic Server?
Since the February 2023 acquisition, MarkLogic is a Progress brand.
MarkLogic Server Competitors
MarkLogic Server Technical Details
Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
---|---|
Operating Systems | Unspecified |
Mobile Application | No |
Frequently Asked Questions
Comparisons
Compare with
Reviews and Ratings
(18)Community Insights
- Business Problems Solved
MarkLogic is a versatile software used by various industries to implement solutions for their clients. It is utilized in publishing workflows, enterprise search, big data analytics, and the semantic web. Users have praised its powerful geospatial search feature, which efficiently searches locations based on latitude and longitude. MarkLogic's indexing and tokenization techniques contribute to the quick execution of search queries.
Healthcare organizations rely on MarkLogic as a backend store for patient records, enabling storage, retrieval, and updates. By using a micro-services approach with patient matching and search functionality, MarkLogic helps keep patients up-to-date across multiple hospitals. It also serves as a central store for companies dealing with large amounts of data across multiple clusters, providing efficient storage and search capabilities.
In the academic publishing field, MarkLogic is extensively used for end-to-end data flow, including metadata and full-text content. Its newer features like semantics and JavaScript support are leveraged to develop cutting-edge technology.
MarkLogic's multi-model approach, scalability, and exceptional performance in handling XML data make it a preferred choice. It is also employed for reporting purposes with potential for future OLTP and OLAP services. Companies utilize MarkLogic to create DataHubs that consolidate data from various sources, enabling business teams to leverage the data with BI tools.
The technology department at Zynx Health relies on MarkLogic as the primary database layer for clinical decision support analytics. MarkLogic's XML-based solution proves valuable in handling hierarchically structured and semi-structured healthcare data.
Attribute Ratings
Reviews
(1-3 of 3)Close to perfect NoSQL DB
- MarkLogic supports fully ACID transaction and I think this is very rare in a NoSQL system.
- The recent version of MarkLogic has Integration with Node.js, REST, JSON which has really made the developers life easier to build integrated systems.
- MarkLogic provides superb documentation for us. It really helps to understand which features work how. Example is- the whole dedicated website for it. https://docs.marklogic.com/
- From the point of infrastructure - Installation, configuration and deployment is very fast. Compared to RDBMS , it's really easy to scale MarkLogic horizontally by adding nodes.
- The licence cost is HIGH.
- The amount of space required to store the data seems high hence costly.
- The compatibility with legacy system is not yet available. I feel this area needs to be improved very fast.
- Performance
- 90%9.0
- Availability
- 90%9.0
- Concurrency
- 80%8.0
- Security
- 90%9.0
- Scalability
- 100%10.0
- Data model flexibility
- 70%7.0
- Deployment model flexibility
- 70%7.0
- Generally speaking, it has positive effects on the product. ROI is kind of ok as the licensing cost is bit higher.
- Flexible Data Model and Universal Index features of MarkLogic, will help you for sure in achieve quick ROI. For long term you need to think.
MarkLogic- The Swiss Army Knife of data platforms
- MarkLogic does everything well, but search is the "bread and butter" operation. All data is indexed on-the-fly and the API's offer a multitude of ways to create incredibly powerful search applications. The search engine isn't bolted on- it's at the core of the database. Search suggestion, relevance, advanced grammar, spell correction (did you mean?), paginated search over massive numbers of records, etc. is all at the fingertips of the developer. The database scales to massive size and yet search returns sub-second results for the most complex search parameters.
- High availability, disaster recovery, and scaling is handled incredibly well. In the AWS cloud, it is trivial to set up a MarkLogic system to elastically scale with data and request volume- truly elastic, adding nodes and removing them as needed. Databases can replicate to a remote datacenter in real-time to provide instant cut-over for datacenter loss. Clustered servers provide highly available replication of data to instantly recover from node failures.
- Security is increasingly important as data takes center stage in an enterprise. MarkLogic's role-based security is baked in to every query. This is battle-hardened content control.
- Flexibility is unrivaled. Any data can be stored reliably and securely in the MarkLogic database. Records can be stored as text, XML, JSON, or binary. All text, XML, and JSON is instantly indexed and the various strategies for indexing are easy to configured and well documented. MarkLogic is also a powerful semantic triple store. Unlike any other NoSQL solution, MarkLogic can handle full documents, graphs, key-value pairs, binaries, etc. in a single database, providing powerful and unique ways of combining enterprise data.
- MarkLogic still has a long way to go in fostering the developer community. Many developers are gravitating to the simple integrations and do not delve into the deeper capabilities. They have made tremendous strides in recent months and I am sure this will improve over time.
- Many of the best features are left on the floor by enterprises who end up implementing MarkLogic as a data store. MarkLogic needs to help customers find ways to better leverage their investment and be more creative in how they use the product.
- Licensing costs become a major hurdle for adoption. The pricing model has improved for basic implementations, but the costs seem very prohibitive for some verticals and for some of the most advanced features.
- Mission critical nature of your data
- Complexity of your data- do you have polystructured data?
- Data volume- MarkLogic can handle few records, but it's really meant to house significant volumes of data.
- Composition of your development team
- Lifecycle of your system
- We've had customers who have been able to save their organization hundreds of thousands of dollars by preventing duplication of costly processes. Powerful search capabilities into what different business units had available drives better decisions.
- Ability to receive content in personalized ways has lead to significant new sales opportunities for some of our customers. This personalization includes on-demand publishing of specific articles on specific topics in addition to recommendation engines and shopping cart analysis.
- One customer that has an extremely advanced application leveraging nearly every feature MarkLogic has to offer found nearly 3:1 cost savings using MarkLogic when they performed an analysis of projected development and maintenance costs to replicate all their functionality on open source stacks.
In addition to MarkLogic's direct support, there are several employees who are very active among the community and many questions and common issues get quick attention from helpful responses to email and StackOverflow questions.
- Search is very elegant, flexible, and powerful.
- Backups and restore are relatively pain-free. Especially compared to other systems.
- Query Console is a very powerful tool that helps a new developer understand how to code/interact with the server as well as provides access to data.
- Installation and upgrading is really easy. System admin is generally easy as well.
- MarkLogic has made good progress, but the system architecture does complicate deployment as compared to other application servers.
- Replicating massively large datasets across servers can be tough sometimes. Again, some methods are pretty good, but may not always be feasible. By massive, I mean tens of millions of records, many GB of data, so nothing really does that easily.
Can You Bet on It?
- MarkLogic is fast and flexible. The data does not have to be structured (particularly in advance).
- MarkLogic is a combination database, search engine, and application server. As a database, it is ACID compliant which is absolutely essential for mission critical production applications.
- MarkLogic is dependable, in almost all cases recovers by itself, and is relatively easy to administer.
- MarkLogic is not cheap, either for the software itself, the hardware to run it on, or the investment in learning necessary to use it effectively. While MarkLogic has gone to great pains to add multiple interfaces so that a deep understanding of XQuery is theoretically not necessary, I feel XQuery is essential to understanding the product well enough to use it in production applications.
- Specifically, it is my understanding that switching database contexts is expensive in terms of performance. There could be be a improvement in the ability to query across databases, or even across clusters, that could drive greater flexibility in design decisions.
- The security model definitely could be improved to facilitate sharing users, roles, and permissions across clusters. Building your own security model to allow users access to data on different clusters is very complex and leads to a number of performance issues.
- It took longer than expected to develop our application and get the level of consistent performance necessary. As a result, profit was flat for a couple of years but the benefits are really starting to kick in.